Pull-Request requirements

Mandatory Review for All New Flight Controllers

• All new flight controllers must undergo the Betaflight review process, regardless of whether they use an existing target.
• Manufacturers may reuse the same target for multiple designs, but each new hardware release must be reviewed before approval.

Hardware Compliance Requirements

• All hardware must adhere to the Manufacturer Design Guidelines.
• Poor hardware designs will not be accepted, as outlined in the Requirements for the Submission of New and Updated Targets.
• Adhere to the [Config Target Guidance] https://betaflight.com/docs/development/manufacturer/config-target-guidance
• To avoid costly issues and delays, we strongly encourage consulting with Betaflight developers early in your design process and providing schematics for review before producing hardware.

These measures help maintain high standards and ensure compatibility within the Betaflight ecosystem.

If you have any questions or need guidance, feel free to reach out to the Betaflight development team.

Housekeeping

• Pull-Request only from a custom branch, not master.
• Replace this text with details of your own.

Checklist (✓/✕, or y/n)

• passed Betaflight team's schematics review
• passed hardware samples testing
• follows guidelines
• follows connector standards
• flight tested
• comments/issues resolved

Summary by CodeRabbit

• New Features
  • Added support for the HGLRC_F722_S flight controller: onboard accelerometer & gyro, barometer, and I2C magnetometer.
  • Onboard flash for Blackbox and OSD support, inverted beeper, motor outputs, and addressable LED strip.
  • Multiple UART/I2C/SPI ports with ready-to-use pin mappings and default hardware topology.
  • ADC-based current/voltage sensing with default scaling and DMA optimization, plus sensible runtime defaults (blackbox device, gyro yaw alignment).

_{✏️ Tip: You can customize this high-level summary in your review settings.}